|
|
| Author |
Thread Statistics | Show CCP posts - 3 post(s) |
Matuk Grymwal
Lapse Of Sanity
Exhale.
2
   |
Posted - 2012.04.07 10:26:00 -
[1] - Quote
Yeah same issue here. Based in Aus, and am randomly losing connection to the server. If I have multiple clients going I usually lose all of them at the same time. Will try to get more diagnostic info, trace routes, etc. |
Matuk Grymwal
Lapse Of Sanity
Exhale.
2
|
Posted - 2012.04.11 09:44:00 -
[2] - Quote
CCP Mort wrote:ok - we are not ignoring you guys ...
so, about ping tests - has anyone seen packetloss with ping/ping plotter tests to 87.237.38.200 - at the same time you are thrown out of EVE ?
so.. for the tech's - open a cmd window - have a ping 87.237.38.200 -t running in the background...
do you lose pings when thrown out of the game ?
Traceroutes are good for me to see the path/what provider you are using, and request-timeout in the traceroute only means a router in the path is not replying to the traceroute tool.
- Mort
Yes, yes and oh god yes. I've been retesting this tonight using ping plotter. I'm actually coming in through a different route now than when I first saw the problem, but I'm still getting packet loss. Usually its in short bursts, but occasionally it goes up to over half a minute, and that's when I drop. I'm now getting the loss in node #16 (ix-12-0-0-3045.core4.LDN-London.as6453.net):
Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Vigor.router [192.168.1.1]
2 16 ms 16 ms 15 ms nexthop.nsw.iinet.net.au [203.215.19.247]
3 16 ms 16 ms 16 ms te1-1.syd-mas-bdr1.iinet.net.au [203.215.18.18]
4 15 ms 15 ms 16 ms xe-1-1-0-0.syd-mas-core1.iinet.net.au [203.215.20.94]
5 16 ms 101 ms 95 ms ae0.syd-ult-core1.iinet.net.au [203.215.20.110]
6 17 ms 16 ms 16 ms 26629.siko06.cu.reach.com [134.159.126.45]
7 17 ms 17 ms 17 ms i-0-2-4-0.sydo-core01.bi.reach.com [202.84.223.5]
8 135 ms 136 ms 135 ms i-4-0-0.siko-core02.bx.reach.com [202.84.140.138]
9 137 ms 138 ms 138 ms i-0-2-0-0.siko01.bi.reach.com [202.84.219.46]
10 * * * Request timed out.
11 390 ms 407 ms 388 ms if-9-2.tcore2.PDI-PaloAlto.as6453.net [180.87.180.17]
12 389 ms 389 ms 387 ms if-2-2.tcore1.PDI-PaloAlto.as6453.net [66.198.127.1]
13 409 ms 392 ms 394 ms if-13-2.tcore2.NJY-Newark.as6453.net [66.198.127.46]
14 353 ms 354 ms 360 ms if-2-2.tcore1.NJY-Newark.as6453.net [66.198.70.1]
15 392 ms 392 ms 392 ms if-9-0-0.core4.LDN-London.as6453.net [66.198.70.130]
16 * 421 ms 425 ms ix-12-0-0-3045.core4.LDN-London.as6453.net [195.219.67.242]
17 423 ms 422 ms 422 ms srv248-e.ccp.cc [87.237.36.248]
18 423 ms * 423 ms srv200-g.ccp.cc [87.237.38.200]
Trace complete.
FYI: for affected pilots, as a temporary work around for the issue I have been using the trial version of Battle Ping (server connection was rock solid when I used it). If it's still an issue in a few days, I guess I'll be buying a copy.
-Mat |
Matuk Grymwal
Bite Me inc
Exhale.
2
|
Posted - 2012.04.12 13:39:00 -
[3] - Quote
So I've had ping plotter running all (AU) evening, so from before DT to 3 hours after. Since DT I've seen one block of about 30s of packet loss (which is generally long enough to disconnect eve). However completely green otherwise. Certainly better. |
Matuk Grymwal
Bite Me inc
Exhale.
2
|
Posted - 2012.04.14 09:28:00 -
[4] - Quote
I'm seeing the same behaviour after the first tweaks were made a couple of days ago. I.e. it's a lot better as I rarely get packet loss but I still get the occasional extended period of packet loss which is long enough to disconnect the client. |
|
|
| |
|